Fullscreen Image

Accruent Siterra 26.3 Release Notes

We're delivering this automatic upgrade to UAT environments on May 14, 2026 and to production environments on June 6, 2026.

Release notes are subject to change until the production release.

Preview new interface

We’re continuing our roll out of a new modern interface for Siterra. Early adopters can sign up to evaluate it.

The preview is unavailable by default. To request access, contact Accruent Support with this subject line:

Request technical preview of new Siterra UI in UAT

When Support enables the preview:

  • Select New Siterra (upper-right) to switch to the new interface.

  • Select it again to return to Classic Siterra.

Most menus and options work the same in the new interface. If you open something that isn’t available yet, Siterra shows the Classic page or dialog and continues operating normally.

Review what we've added to the new Siterra preview in each release.

Calculated extended attribute functions: IS_NULL() and IS_BLANK()

SP-56228, SP-58588, SP-59254

Administrators can now use the IS_NULL() and IS_BLANK() expression field functions in calculated extended attribute formulas to check whether a referenced field contains a value. This makes it easier to create conditional logic that identifies missing information in forms, grids, and reports.

Function

Description

IS_NULL({field})

Returns TRUE if the referenced field has no value. For text fields, use IS_BLANK() to check for no meaningful content, including empty or whitespace-only values.

IS_BLANK({field})

Returns TRUE if the referenced field is effectively blank for its data type. For text fields, this includes null, empty, and whitespace-only values. For date fields, it means no date is entered. For lookup fields, it means no selection is made. For number and Boolean fields, only null is considered blank. 0 and FALSE are valid values and are not blank.

Example

IF(IS_BLANK({Start Date}), "Not set", "Has date")

Recommended usage

Use IS_NULL() and IS_BLANK() instead of comparing directly to empty strings, 0, FALSE, or default dates when you need to check whether a referenced field contains a value.

Improvements and issues fixed

Component

Summary

Reference #

API

Authorized API users can now download multiple document revisions from a subtask in one HTTP request. This aligns with downloading multiple revisions in Siterra.

Example endpoints:

  • GET /Documents/v1/Subtasks({subtaskId})/Revisions

    The response now includes FileName and FileSize.

  • POST /Documents/v1/Subtasks({subtaskId})/DownloadRevisions

    Downloads selected revision IDs as a single ZIP file. Non-admin users with Read permissions can use this endpoint.

Administrators can configure download limits including maximum file count and total size per domain. Contact Accruent Support if you need help setting these limits.

SP-59563

Customer idea

API

Authorized API users can now save a task’s form extended attribute data without completing the task. This matches the legacy SOAP behavior of Tasks.asmx.SaveFormTask(sessionId, projectNumber, taskNumber, extendedAttributes[]). This helps you migrate from the SOAP API to the RESTful API while keeping existing workflows unchanged.

Example endpoints:

POST /projects/v1/SaveFormTask

Example payload:

{	
  "ProjectNumber": "PRJ-10001",	
  "TaskNumber": "TASK-20002",
  "ExtendedAttributes": [
     { "Id": 123, "Name": "FieldXmlNameOrLabel", "Value": "Some value" }
   ]
}

SP-59599

API

 

Authorized API users can now update a task’s ActualEndDate without sending ActualStartDate. If the task already has a valid ActualStartDate, the API keeps it unchanged and completes the request successfully.

Example endpoint:

PATCH /projects/v1/Tasks({taskId})
**Example payload (end date only):**
{
	"ActualEndDate": "2026-04-09T00:00:00Z"
}						

If the task does not already have a valid ActualStartDate, or if the new ActualEndDate is earlier than the stored ActualStartDate, the API now returns clearer validation messages.

Administrators configure whether updating actual dates requires task completion using the PATCH_ACTUAL_DATES_REQUIRES_COMPLETION setting. Contact Accruent Support if you need help updating this setting.

SP-59621

Bulk Object Updater (BOU)

The BOU Subtask Extension now correctly supports multiple selections for the same subtask type. BOU users can select and update multiple approval subtasks or multiple document subtasks in a single view, up to the existing limit of 40 subtasks. Form subtasks remain single-select by design, helping prevent unintended bulk updates across multiple forms.

SP-59565

BOU

BOU now keeps your attribute filters visible and easier to understand. When you filter by a Standard Atttribute or Extended Attribute, the selected attribute is clearly displayed in the view and, when possible, shown directly in the grid. This makes it easier to see exactly which attributes you are filtering on and how they affect your results, without changing existing filtering behavior.

SP-59629

BOU

BOU now handles task permissions more clearly and consistently when you:

  • Mark a task as N/A or remove N/A

  • Set or remove Manual Dates

If you don’t have the required permission for an action, BOU now deactivates the related option.

To enable this improvement, contact Accruent Support.

SP-59649

BOU

If the role you are assigned has Project Task & EA data [Restricted permissions], and you select a form in the Project Task & EA data view of BOU:

  • The grid now honors the form’s required and read‑only rules for Extended Attributes (EAs).

  • Required EAs are indicated, and require you to enter a value before saving changes.

  • Read‑only EAs are indicated. You can’t edit them in bulk.

  • When you select multiple forms, the grid calculates required and read‑only status based on the rules defined on those forms.

This builds on the role‑based permissions we delivered in Siterra 26.2.

SP-59482

BOU

In the Project Task & EA data view of BOU, form-based triggers for Task Groups now run only in the Subtask Extension view, where you complete tasks one at a time. This change keeps trigger execution reliable, consistent, and helps avoid unexpected results during bulk edits and saves in the Task & EA view.

SP-59485

BOU

BOU search results now include dynamic links that make it easier to open the related record. When this feature is enabled, select an item in your BOU results to navigate to the item on object's Home page.

To enable this improvement, contact Accruent Support.

SP-59646

Calculated attributes

When you change a date-only calculated attribute, the hover tooltip now correctly shows the previously stored date instead of the new value. The tooltip also displays dates without a time component, so the information is clearer and consistent with date-only fields.

SP-59489

Crue

When you select a link in an Ask Crue response in Siterra, the link now opens correctly in a new browser tab and that tab becomes active. This enables you to quickly access linked content without losing your current Ask Crue session.

SP-59670

Download Zip

Select Download Zip on any Site homepage to generate the ZIP file and download it to your browser's download folder. If an error occurs during ZIP file generation, that message displays. No silent failure occurs.

SP-59214

Escalations

Escalation amounts you create using Add Multiple now calculate correctly when the escalation amount frequency differs from the payment line frequency. For example, annual escalations on monthly payments. The system now converts the escalation amount to the payment line frequency once, so each escalation applies a consistent and expected increase.

SP-58899

Extended Attributes

ADDDAYS date calculations now return a Date value with instead of DateTime. This ensures that follow-on calculations receive dates in the correct format for the user’s locale with no time component. This change is backward‑compatible for existing formulas.

SP-57386

SP-59246

Import tool

Valid recurring payment files now import successfully without the “Object reference not set to an instance of an object” error when they pass a Dry Run, enabling you to load and execute payment files with confidence.

SP-57583

SP-59076

Projects

When you create projects by import with a valid role set applied in a single step, the import tool now validates role set compatibility during dry run and execution, and successfully creates the project when the role set is allowed for the selected project template. This helps you avoid follow‑up update imports and keeps dry run and execution results consistent.

SP-59207

Projects

When you create projects under a search ring, the Search Ring ID is now saved correctly. This ensures projects created from templates under search rings remain correctly linked. Projects that are not under a search ring continue to save a NULL Search Ring ID as expected.

SP-59506

Sites

The Edit Site page now loads the saved Type value for each site and no longer displays a default value unless you saved that value. This helps protect your reporting accuracy and prevents unexpected changes to site classifications.

SP-59256

Sites

Site Type no longer changes to the first lookup value when opening the Edit Site window. The field now consistently displays the site’s saved value, improving data accuracy and reporting reliability.

SP-58769

Task Groups > Where Used

The Task Group > Where Used view now correctly maps task groups to their related records and displays accurate counts in the chart. This helps administrators and users quickly trust what they see in the Where Used dialog without having to cross‑check data in other reports.

SP-54627

To-Dos / Activity

From and To date filters in the Tasks Pending Approval section of the To-Dos / Activity page now correctly accept dates you enter manually. Enter dates in any supported format configured by your administrator, such as MM/DD/YYYY or DD/MM/YYYY.

SP-59197

SP-59236

Project templates

Project templates now correctly save edits when the Auto Set Baseline Dates feature is toggled off.

SP-58957

Log

Document upload subtasks now correctly show the user who completed the upload using the Bulk Object Updater (BOU) document upload extension. The Last Action field accurately shows who carried out the upload, improving audit accuracy and log reliability.

SP-55653